Parallel computing system, method and architecture

ABSTRACT

A parallel or computing system and method make use of a plurality of adapters each affording a specific type of processing algorithm. At each point in an application, an adapter is identified, to parallelize that portion of the application. The process involves associating an appropriate adapter with the application portion, parsing the application portion to define tasks that may be distributed over the available computers. Combined with the parallelized program is a software server that is designed to cooperate with the adapters to control and supervise distributed processing functions. Such functions include mapping, load balancing, and error detection and correction. Also included are functions that cause the results of the computing to be coordinated in real-time and returned appropriately, according to the application. In addition to the parallelized program and server, an application created by the present invention is provided with the functionality of virtual middleware, which interfaces with and controls existing forms of middleware.

CROSS-REFERENCE TO RELATED APPLICATIONS

This continuation patent application claims the benefit of priority ofU.S. patent application Ser. No. 10/310,115, filed Dec. 4, 2002, whichclaims the benefit of priority under 35 U.S.C. §119 of U.S. ProvisionalPatent Application Ser. No. 60/338,278, filed Dec. 4, 2001, entitled“Parallel Computing System And Architecture,” the entirety of which ishereby incorporated by reference.

FIELD OF INVENTION

The present invention relates generally to parallel computing and, moreparticularly, concerns a software system, method and architecture thatpermit existing and new computer programs to be converted, at thealgorithm level, for true parallel processing.

BACKGROUND OF THE INVENTION

Various businesses have a need to run computer applications involvingextensive computer processing, and computation time can be a vitalfactor in the success of the business. Hence there is a perpetual questfor increased computing power and reduction in computational time. Forexample, in the financial industry, there are many computationalintensive factors, including: pricing and hedging complex derivatives;portfolio-pricing, hedging and risk (market, credit, and operational)calculations; value at risk calculations, end of day marked-to-marketprocessing and report generation; and calibrating financial model tomarket.

The computation time can have a critical impact on the value andusefulness of the calculations. Continuing with the financial industryexample, the 5 and 7 year Euro Dollar basis may be slipping relative tothe 10-year swap one hour before the close of the financial-markettrading period. The fixed income derivatives desk needs to re-calibrateits multi-factor model and re-hedge it's interest rate and volatilityrisk immediately because of conditions resulting in substantialvariability of the yield curve. If the desk does not hedge, it will havea significant loss. Typically, it takes 30 minutes to re-calibrate amulti-factor model; 2 hours for mark-to-market of the portfolio; and 3hours for risk reports; in all, 5 hours. In this situation, the deskcannot respond adequately in a timely manner and will likely put acostly, inaccurate hedge in place.

One way to solve large, complex problems in real time or minimum time isby using a supercomputer such as the Cray. Of course this option is verycostly and not practical for the typical business.

Another way to achieve substantial computing power is through parallel(simultaneous) processing. Inexpensive off-the-shelf-processors, such asrecent Pentium and Alpha chips have become very powerful, and they canbe harnessed together in parallel for increased processing speed.Certain computers, mainly servers, have been provided with multipleprocessors to share the processing load, speeding overall operation. Ona higher level, multiple computers have been linked together over anetwork in “cluster computing” arrangements, to act like a virtualcomputer. The basic concept is that the processing workload of anapplication is split into manageable sections that are distributed amongthe networked computers, to achieve relatively quick solutions ofcomputational problems that are normally time-consuming. However,computer clusters perform distributed computing without controlling thereturn of results. On the other hand, the ideal of parallel processingis to achieve true parallel computing, which provides intelligentparsing and mapping of the workload to different processors, faulttolerance of the workload activity, balancing of the work, coordinatingreturn of results, and scalability. Although systems achieving a degreeof distributed computing have been available, true distributed, parallelcomputing has not been achieved until the present invention.

There are three general levels in the hierarchy of distributedcomputing. The simplest is task distributed processing. At this level,the identical application is run on multiple computers in a cluster,with a different set of initial parameters being passed to eachcomputer. In order to achieve this level of distributed processing of anapplication, a user must develop a substantial amount of code toimplement that processing. Commercial systems have been available toaccomplish this, but they permit distributed processing of only thesimplest linear problem.

At the second level of the hierarchy is data-distributed processing,which permits the computations of iterative processing loops in anapplication to be distributed across a computer cluster. To make use ofthis form of distributed processing in an application, substantialmodification of the code internals and loop processing are necessary todevelop the application. Even then, parallel computation is limited tothe loop components and is not achieved at an algorithm level. Also, theheavy data distribution tends to utilize significant bandwidth, causingcongestion in networks. This form of distributed processing may be usedfor linear problems but not non-linear problems. At least one commercialsystem has been available which achieves this level of distributedprocessing.

At the top of the hierarchy is algorithm distributed processing, inwhich the algorithm of an application is itself distributed among thecomputer cluster. This is achieved within the program itself bydynamically distributing the algorithm directives. This form ofdistributed processing is also lower in network bandwidth usage, becausedistribution is limited to the algorithm rather than a voluminous amountof data. Systems achieving algorithm distributed processing have notbeen available commercially.

Cluster middleware is used to interface between the server requestingdistributed processing of an application and a computer cluster, toachieve distributed processing. The middleware is typically executablecode made available by a vendor, which must be incorporated into anapplication adapted for distributed processing. The user must write asubstantial amount of code to interface properly with the middleware andto utilize its available features.

As already explained, the most effective parallel computing involvesdistribution of tasks at the algorithm level of the program. Mostcomputing falls into basic types of known algorithms. Some commonalgorithms are linear (structured); nonlinear (complex structure); MonteCarlo; non-recombining tree; Complex Monte Carlo; Branch & Bound(Multidimensional Solver); and Associative Network.

Existing parallel computing implementations fail to provide the capacityto parallelize paradigms except for the simplest linear type. In manyindustries, front, middle and back offices utilize diverse algorithmsand applications. Many of these applications are time sensitive andmission critical and therefore require reduction in computation time andan increase in result accuracy. Diverse groups within enterprisesrequire a universal parallel computing platform, ease of deployment ofexisting applications to a parallel computing platform, and ease ofcreation of new applications for a parallel computing platform.

What is needed in the art is the capacity to run essentially anyparallel computing program on any distributed network. In particular infinancial services and energy companies there is a strong need for ascalable distributed computing platform. The present invention solvesthese and other needs.

SUMMARY OF THE INVENTION

The present invention provides a system, method and architecture toachieve a true parallel computing infrastructure. This infrastructureprovides the capability to transform an application into a parallelcomputing program and facilitate execution of the resulting program onan existing network of computers. The system and method effectivelyallow any algorithm-based application to operate on essentially anyplatform. The present invention may be used to model and deployvirtually any type of parallel computing paradigm to solve any type ofcomputationally intensive problem.

The parallel computing method in accordance with the preferredembodiment of the invention makes use of a plurality of adapters eachaffording a specific type of processing algorithm. At each point in anapplication, an adapter is identified to parallelize that portion of theapplication. Specifically, the process involves associating anappropriate adapter with the application portion, parsing theapplication portion to define tasks that may be distributed over theavailable computers. Combined with the parallelized program is asoftware server engine (Lobster), which is designed to cooperate withthe adapters to control and supervise, distributed processing functions.Such functions include mapping, load balancing, and error detection andcorrection as well as work splitting, distribution to slave computers,and gathering and coordination of results. Also included are functionsthat cause the results of the computing to be coordinated in a real-timeand returned appropriately, according to the application. In addition tothe parallelized program and Lobster, an application created by thepresent invention is provided with the functionality of virtualmiddleware (DNET), which interfaces with and controls existing forms ofmiddleware.

In accordance with one aspect of the present invention, a method forparallelizing an application is provided. In that method, a plurality ofadapters are provided, each affording a specific type of processingalgorithm. At successive portions in an application, an adapterappropriate for parallelizing that portion of the application isidentified and associated with the portion. A code segment whichrepresents the functionality of for each identified portion and whichincludes a call to a client-server library is generated, and a call tothe client-server library is included in the application which, atrun-time, launches said codes segment from a main entry point in eachrespective code segment in lieu of executing the portion.

In accordance with another aspect of the present invention, a method forrunning a parallelized application in which a pool of work is to beperformed is provided. In that method, a master server that operates ina master mode is used to instantiate a stateless server which contains afirst object including a code segment suitable for processing work fromthe pool. The master server dispatches to the stateless server a firstportion of work from the pool. Reports are provided to the master serverconcerning the progress of the first portion of work dispatched to thestateless server, and additional portions of work are distributed fromthe master server to the stateless server once a prescribed amount ofwork progress has been reported by the stateless server.

A salient aspect of the foregoing method is that the stateless servercan be established either in a slave mode, or in a dual mode including amaster mode in which the stateless server serves as a master to otherservers.

These and other aspects, features and advantages can be appreciated fromthe attached figures and the accompanying description of certainembodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing brief description, as well as further objects, features,and advantages of the present invention will be understood morecompletely from the following detailed description of a presentlypreferred but non-the-less, illustrative, embodiment in accordance withthe present invention, with reference being had to the accompanyingdrawings in which:

FIG. 1 is a functional block diagram illustrating a traditional parallelcomputing system architecture;

FIG. 2 is a functional block diagram illustrating how parallel computingis enhanced in accordance with a preferred embodiment of the presentinvention;

FIG. 2 a is a functional block diagram illustrating further details of aparallelized application in accordance with a presently preferredembodiment;

FIG. 3 is a graphic representation of the core architecture for parallelcomputing system embodying the present invention;

FIG. 3 a is a graphic representation of the architecture for aparallelizing and parallel-operating computing system in accordance witha presently preferred embodiment;

FIG. 4 is a flow chart illustrating steps taken in a preferred methodfor generating code segments usable in parallelized application;

FIG. 5 is a graphic representation of an application showing its logicalarrangement before and after parallelizable code segments have beengenerated;

FIG. 6 is a graphic representation of master and slave code segments;and

FIG. 7 is a graphic representation of multiple code segments in ahierarchical arrangement illustrating the single- and dual-modecapabilities of servers in accordance with the preferred embodiment.

DEFINITIONS

As used herein, the following terms shall have the meanings statedbelow.

“Application” is an existing software product that is to beparallelized. That product is parsed to identify portions that canexecute in parallel. Each portion has at least one algorithm.

“Client/Server Library” is used to deliver the program to the user forparalleling portions of the application.

“Cluster” is a collection of resources (usually servers or workstations)used in a computation in an effort to speed up program execution. Thisterm is often used in the context of the Internet servers to refer to aset of web servers connected together for fail-over andhigh-availability purposes.

“Decomposition” refers to the process of breaking a piece of work downinto smaller computations that can be executed on different computers.

“High Performance Computing” or “HPC” is the application of parallelcomputing practices to a problem set in order to speed up applicationexecution time or to be able to handle more data.

“Message Passing Interface” or “MPI” is a collection of applicationProgramming Interfaces and message passing primitives used to createparallel programs.

“Parallel Virtual Machine” or “PVM” is a programming environmentdeveloped at Oak Ridge National Laboratories that supports a series ofmessage passing and process management operations.

“Parallelization” refers to the process of turning a sequentiallyordered set of programmatic operations into a set of smaller operationsthat can be executed substantially independent of one another for thepurposes of speeding up the overall computation.

“Program” is the software that embodies the lobster engine, makes callsto a client/server library, and includes an extensible set of adapters.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENT

FIG. 1 is a functional block diagram illustrating traditional parallelcomputing technology. In this example, parallel computing is to beachieved for three programs, Programs A, B and C, via clusteredcomputers 1-n. One hardware-based master server controls all parallelcomputing activities. The server, however, lacks specific knowledge ofthe different types of problems being handled in each program: it hasnetwork workload knowledge, but no “problem” workload knowledge.Accordingly, resources are utilized inefficiently. In addition, themiddleware is hard-coded in order to permit appropriate communicationwith computers 1-n. Should the master server fail, there will be asystematic collapse of virtually all parallel computing processes.Moreover, any effort to replicate the master server is highly technical,cumbersome, and unlikely to succeed.

FIG. 2 is a functional block diagram illustrating how parallel computingis enhanced in accordance with an embodiment of the present invention.In the present example, applications A-Z are to be process in parallelon a cluster comprising computers 1-3. As will be explained morecompletely below, applications A-Z have been modified, utilizingadapters in accordance with the present invention, in order to obtain anapplication that achieves algorithm-distributed processing. In addition,a software-based server has been embedded into each program, thesoftware servers collectively defining a virtual main server. Each ofthe software servers is aware of the specifics of its algorithm portion,allowing for precise parallel-computing resource allocation. Moreover,failure of a particular application portion has no effect on the otherapplication portions being processed in parallel therewith. A particularserver can be replicated automatically to execute the correspondingportion on another machine. In the preferred embodiment, each server iscalled a LOBSTER (LOad Balancing Sub-Task Executer).

Also present in each program is virtual middleware, which is designed asa universal interface to all available middleware. Thus, the serverwithin the application is able to take full advantage of all featuresavailable in every type of middleware. In the present example, this hasenabled peer-to-peer communication among the computers 1-3. In thepreferred embodiment, the virtual middleware is called DNET (DistributedNETwork).

Thus, the invention provides an application service layer that speedsthe development of computationally intensive and data intensiveapplications, and an application framework with all of the functionalityneeded to support a fully parallelized application.

The software program that includes the adapters and lobster (includingthe main server and problem/algorithm applying components of FIG. 2)comprise a program 20 that parallelizes the user's application 60, andmanages its parallel operation it run-time. FIGS. 2A and 3A providefurther details of the interaction of a particular user application 60and this program 20.

In FIG. 2A, a single user application 60 is illustrated; however, itshould be understood that the methodology and system of the presentinvention can be operated with multiple user applications, generally asindicated in FIG. 2. The user application 60 can comprise any sort ofapplication, but for purposes of illustration only, the user applicationis described by way of example as the Microsoft Word™ word processingprogram. The user application 60 includes a number of portions 60A, 60B,etc., which illustratably can be a word count routine, a spell checkroutine, and any number of other routines that would typically exist ina word processing environment. In the context of other user applicationssuch as those used in the financial services industry, the portions aresuitably configured to implement particular algorithms such as creditmodels, values at risk, Peter Carr models, and the like. It is common inthe development of applications, at the present time, to periodicallyrely upon libraries such as the Microsoft library 62 to source one ormore of the portions from a location that is external to the application60 itself, yet which interact with the application 60 provide fullfunctionality to routines that are within the applications, either asembedded routines or as routines selected by a user through aninterface. Such a user library 62 can be used with multiple userapplications, for example, the same library routine that is utilized byMicrosoft Word can be utilized by other Microsoft applications, such asMicrosoft Excel.

The various portions of the user application 60 are generally referredto as portions 60A, 60B, 60C, etc.

The program 20 includes an extensible set of adapters 10 that cooperatewith a lobster engine 22 to map out the algorithm specified in aparticular portion 60A, 60B of the user application. One adapter in theset will be most suitable for a given portion, or the user can define anew adapter to address specific needs of a given portion.

The program 20 can generally be considered as comprising three layers.At the top layer there is a user interface 24 which includes the set ofextensible adapters 10. Below that layer is the lobster engine 22 whichincludes a number of software constructs that permit portions of theuser application 60, (which have been processed by one of the adaptersor by an adapter SDK 12) to be utilized by the engine in a faulttolerant and load balanced manner. Below the lobster engine is anexecution layer 18 which is primarily concerned with the networkresources that are available at a given time to the program 20. Theexecution layer 18 is concerned with fault tolerances and resourcemanagement issues concerning the computers and other machines that areconnected to the network 4 rather than to the stability and operation ofany particular mapped portion 60A, 60B, etc. The foregoing layerdescriptions are to assist in an understanding of the architecture ofthe program 20, and are not true divisions in the program itself.

With further reference to FIG. 2A, once the user application 60 has beenprocessed by the program 20, individual portions can be farmed out tothe available resources on a remote network 4. As will be describednext, each of the portions is analyzed by the program 20 to determinewhether parallelization is possible, and for code that can beparallelized, one or more algorithms within that portion are adapted andthen distributed to the computers on the network 4, and the results arereturned to the respective adapter that issued that work for handling atthe network 4. This process is repeated for a number of algorithms andfor a number of subparts of specific algorithms among and betweenvarious portions 60A, 60B, etc. of the user application. Concomitantly,the lobster engine provides a management role to ensure algorithms arebeing processed, results are being returned, and there is a load balancein the processing of any ranges within a given portion that has beenassigned to a specific adapter. As well, the execution layer 18simultaneously monitors the resources that are available to the lobsterengine to ensure that results are being returned and that confrontationintegrity remains intact.

In one aspect, the invention includes a mechanism for attaching thedeveloper's algorithms into the parallel framework. That work isperformed by a set of “adapters” 10 which operate upon the portions 60a, 60 b, etc. An API shields users from all parallel computing issues.The user writes call-backs that supply the main logic of the portion(s)being parallelized to the application 60. Software in accordance withthe preferred embodiment uses these call-backs to drive the application,controlling work break-up, distribution to remote compute resources, andthe gathering of results. Specifically, basic decomposition functionsare used to break-up computational processes in the application 60 intoportions that can be run independently of or dependently on one another(i.e., the portions can be individual libraries, dlls, or executables),allocating the portions to slave processors, and gathering the resultsto produce an answer. That work is performed by a “Lobster” engine.

In the decomposition of a program into sub-tasks, the user converts anexisting application to a form more amendable to parallel processing. Inthe traditional approach to parallelizing a program, a developer had todecompose a function into parts that can be performed as paralleloperations and then write MPI or PVM code to make the application splitwork into M ranges, send the ranges to each of the slaves, have theslaves process the work and send the results back to the master, andhave the master receive the results and aggregate the pieces into aresult. These are non-trivial tasks that burden the parallelizingprocess and generally restrict the applicability of the so-parallelizedprogram to its present incarnation.

In accordance with the invention, a plurality of adapters 10 areprovided to ease the parallelization process. Each adapter 10 defines atemplate for a specific type of problem and provides developers with aframework for adapting their applications 60 to run in parallel. Theadapter framework is preferably based upon a set of object-oriented baseclass adapters. To enhance or extend the adapter features one can justinherit the adapter base class. The adapters 10 are callable from C++, Cand other programming languages.

With reference now to FIG. 4, a preferred process for parallelizingportions 60 a, 60 b, 60 c, etc. of an application is described. At step410, portions 60 a, etc., within the user applications 60 areidentified. The act of identifying portions of a user application arepresently performed by the user through interaction with the userinterface layer 24 of the program 20. The user is promoted by theinterface 24 to select the adapter most appropriate to the particularalgorithm presented within a given portion. It is within the scope ofthe present invention to utilize and agent or other intelligent moduleto assist the user in the selection of an appropriate adapter 10;however, the invention is not so limited. At step 420, the user selectsa particular portion to analyze, say, portion 60 a. At step 430, anadapter 10 is selected from the user interface 24. The selected adaptermust be suitable for the particular algorithm contained within thatportion 60 a. As explained elsewhere, the applicability of a givenadapter is a function of the computation of task presented by a givenportion. By way of example, a basic for-next loop is implemented by alinear adapter 10 c. The selection of the wrong adapter will cause anerror log to be written to as well as verbose status information to begenerated that can be useful in guiding the user to a more appropriateadapter choice.

Referring now to FIGS. 4 and 5, the portion 60 a is illustrated asincluding a parallelizable process 70, inputs 72, outputs 74, and othercode 76. Only the process 70 is parallelizable using the adapters 10 andso once an adapter has been selected at step 430, the parallelizablepart of the portion 60 a, namely, process 70, is encapsulated at step440. The act of encapsulating the process 70 essentially comprisesrelocating that code into a code segment 80 which is saved and is usableby the application 60′, via the call-backs to a client/server library 62so that normal program flow can proceed. In addition, encapsulatingpreferably includes alterations to the variables (e.g., theirdefinition, mapping, class, or object form) to operate properly withinthe adapter template.

Depending on the particular portion being parallelized, it is typicalthat at least some code 76 in a given portion will not beparallelizable. Preferably, that other code 76 is included with the codesegment including the parallelizable code so that the bulk of theportion 60 a remains a single unit. Thus, at step 450 the encapsulatedparallelizable process 70′ is combined with the remainder a portion 60a, namely, other code 76, into a code segment 80 that is saved to theclient/server library 62 or elsewhere. The code segment 80 can be anexecutable, a library file, a dll, or some other file structure, savedas indicated at step 460.

At step 470, the process of parallelizing the user application 60 loopsback to step 420 along arrow 480 to select another portion of theapplication to analyze. The process is repeated as described above untilthere are no more portions to analyze and save. When there are no moreportions, the process ends as indicated by the arrow 490.

Referring again to FIG. 5, the user application 60 comprises multipleportions of which only portion 60 a is illustrated in detail. As aresult of the use of the program 20 in accordance with the preferredembodiment of the invention, a user application 60′ results in whichparallelizable processes such as process 70 is replaced with calls to across call interface layer (see FIG. 3 a) that launches the respectivecode segments 80.

An executable code segment 80 with the linear adapter linked-in is aself-contained parallel computing object. Some code segments may not bein an executable form. In either case, the code segment can operate inone of two modes, namely, a master mode or a slave mode. In a mastermode, the inputs 72 and outputs 74 are specified and the process 70 isrun, whereas in the slave mode, only the process 70 is run. If codesegment 80 is configured to operate in the slave mode, it is onlyinvoked at the behest of another copy of the same code segment. Thus, ascan be seen from FIG. 6, a particular code segment 80 a is invoked bythe Lobster engine 22 as a master or slave. Only one code segment 80 awill be a master for a given application 60′. If the code segment 80 adesignated as the master, that segment will first conduct a set-upoperation including, for example, establishing the size of the algorithmto be addressed (sometimes referred to as the “task”) and obtaining thedata required to commence the process (i.e., input data). In addition,the master runs multiple instances of the code segment 80 a in the slavemode in accordance with resources available to the system and theproblem definition at hand. Thus, for example, if two slave instances ofthe code segment are needed to run the algorithm, then two instances 80a′ and 80 a″ will be invoked, with each slave instance running theprocess 70′. Notably, because the additional invocations of the codesegment 80 a are in the slave mode, they ignore any code that directsfurther operations for code segments that have been designated as themaster (via the “if(Master)” programming construct).

Example: Parallelizing an Application Using Adapters

In an application 60 there may be one or more portions 60 a, etc., whichare based on an algorithm. The algorithms may range from a “for loop” toa complex lattice which is composed of many algorithms. The goal is toidentify the algorithm which is computationally and/or memory bound, andaccelerate its performance without restructuring the code or changingthe computational flow. Thus, for example, the linear adapter 10 creplaces the standard “for loop” in a segment of the code in which thecode is taking a long time to compute. The main function of code segment80 is to process a range of the “for-loop” contained in that portion 60a, etc. For example, if the portion 60 a included code such as: for(i =0 ; i < size; i+ +) {  // CODE SEGMENT }

Then, the resulting code segment 80 would have the following code:   intprocess(const int first, const int last) {   int i;   for(i = first ; i< = last; i+ +)   {   // CODE SEGMENT   }

The goal of this example is to show how to build and run a new adaptedapplication that calculates the mean, standard deviation, and standarderror from a sequence of random numbers in parallel: 0 .432944 1 .7647772 .129836 3 .976532 . . . N .389432 Mean .563232 Std Dev .213348 StdError .008387

This type of problem is used in Monte Carlo type calculations. Thechallenge is generating random numbers in parallel withouttouching/modifying the current pseudo random number generator code. Evenmore, the parallel sequence should match exactly to the sequentialrandom number generation.

This problem belongs to a general class of problems called “LinearProcessing.” Linear problems are very prevalent in finance, i.e.,portfolio calculations and risk, matrix of risk, chains of options,volatility grids (surfaces), Monte Carlo, Complex Monte Carlo (LongstaffSchwartz), calibration/optimization, etc. The Linear adapter is used tosolve the above problems and others that can be classified as “Linear.”

The application 60 in this example can comprise the following code:#include <iostream> #include <cmath> using namespace std; //Global varint gSize; double gMult; //Simple Genertor double Random(void) {  return (double) rand( ) / (double) RAND_MAX; } void main(int argc,char **argv) {   //INPUT 72   //Seed   srand(2017L);   //Set Data  gSize = 200;   gMult = 1.;   //PROCESSING 70   double     SUM_CT = 0,    SUM_CT2 = 0,     *randArray = new double[gSize];   for(int i = 0; i< gSize; i+ +)   {     double       randNum = Random( ),       CT  =randNum * gMult;     randArray[i] = CT;     SUM_CT + = CT;     SUM_CT2 += CT * CT;   }   //OUTPUT 74   //Calculate Stats   double     Mean =SUM_CT / gSize,     StdDev = sqrt((SUM_CT2 − SUM_CT * Mean)/(gSize −1)),     StdErr = StdDev / sqrt(gSize);   Cout.precision(12);   for(i =0; i < gSize; i+ +)   {     cout < < i < < ”   “ < < randArray[i] < <endl;   }   cout < < “Mean : ” < < Mean < < endl;   cout < < “Std Dev: ”< < StdDev < < endl;   cout < < “Std Err: ” < < StdErr < < endl;  delete [ ] randArray;   return; }

The code includes input 72, processing 70, and output 74 segments. Inthe input 72 segment, we setup the problem and data. The output 74segment calculates the statistics and displays them. The processing 70segment calculates and stores the random numbers and intermediate datafor the output of the statistical calculations.

The linear adapter replaces the standard “for loop” in a segment of thecode where it is taking a long of time to compute.

In this example, we are not replacing the processing segment 70“for-loop” but replacing the whole sequential application 60 though thatis not required; applying of the adapter to a portion of an application60 could simply generate a code segment that is not an executableprogram in and of itself. Also, the I/O of the example is being replacedby classes. The steps that can be taken to achieve this were generallydescribed in connection with FIG. 4 and are now described in furtherdetail in the enumerated points below in an example that takes theentire portion 60 a, including its inputs and outputs, and creates acode segment 80. This example, therefore, represents an embellishment onthe process of FIG. 4 and the code segment 80 of FIG. 5.

1. Examine the variables in the sequential application and break them upinto the common Input/Processing/Output stages in order to match up theinputs and outputs of the original code with the classes defined for thelinear adapter: Global:   int gSize;   double gMult;   Input(toProcessing array):     double       randNum;   Output (from Processing):    double       SUM_CT, SUM_CT2,       *randArray;

2. Next, compare the template class definition SUM_CT with the abovevariables CT2 (namely, gSize, gMult, randNum, randArray, SUM_CT,SUM_CT2) and create I/O classes from the sequential code. In otherwords, map the variables to the classes required by the selected adapter10. template < class Global,       class InputArray,       class Output,      class OutputArray > class tLinear

Based on the above I/O variables, fill in the template classes asfollows: Global class:   int gSize;   double gMult;

InputArray class—which holds the input random number:

-   -   double Num;

Output (Aggregation) class:

-   -   double SUM_CT, SUM_CT2

OutputArray class—which holds the output processed random number

-   -   double Num;

Alternatively, the InputArray class and the OutputArray class can be thesame class with the template defined as follows: template < myGlobal,      myInput,       myOutput,       myInput > class tLinear

3. To define the code segment 80 (here, an executable) the main entrypoint and the instantiation of linear adapter libraries and the Lobsterlibraries (namely, collectively, the client/server library 62) isachieved through the following code:   //Main Entry point     intmain(int argc, char** argv)     {       Lobster lob(&argc, &argv);      //Input       if(lob.isMaster( ))     }         myGlobal myG(1000,1);         //Assign to Master Global class         gGlobal = myG     }    Linear linear(gGlobal. get_gSize( ), lob);     if (lob.isMaster( ))    {         srand (2017L);         //Add Global class        linear.Add_Input(g-Global);     }       int status = 0;     //Processing     if((status = linear.Run( )) < 0)     {         linear.Print(“Error %d @ line %d\n”, status,         _LINE_);         returnADAPTER_FALSE;     }     // Output     if (lob.isMaster( ))     {        myOutput StatSUM;         linear.Get_Output(StatSUM);        int           gSize = gGlobal.get_gSize( );         double          SUM_CT = StatSUM.get_SUM_CT( ),           SUM_CT2 =StatSUM.get_SUM_CT2( );         double           Mean = SUM_CT / gSize,          StdDev = sqrt((SUM_CT2 − SUM_CT * Mean)/(gSize − 1)),          StdErr = StdDev / sqrt(gSize);         cout.precision(12);        cout < < “Mean : ” < < Mean < < endl;         cout < < “Std Dev:” < < StdDev < < endl;         cout < < “Std Err: ” < < StdErr < < endl;    }     return ADAPTER_TRUE; }

From the above code, the main definitions of the application 60 and itsInput/Processing/Output segments, have not changed. The only change isthere definitions of the variables to classes and the Lobster and Linearadapter library (that is, the client/server libraries 62)instantiations.

4. The code segment 80 is used by the application 60′ via a referencefrom a library. Bn Ctt the reference is known as a member function to anobject such as the linear adapter template. In C, the reference is knownas a call back to a library. Below is an example of a member function toimplement the class global class. //Global Class myGlobal gGlobal; intLinear::FirstProccess(myGlobal &_global) {   gGlobal = _global;   returnADAPTER_TRUE; } //Main Entry point int main(int argc, char** argv); {  Lobster lob(&argc, &argv);   // Input   if(lob. isMaster( )) {    myGlobal myG(1000, 1);     //Assighn to Master Global class    gGlobal = myG; } Linear linear(gGlobal. get_gSize( ), lob); if(lob.isMaster( )) {     srand(2017L);     //Add Global class    linear.Add_Input(gGlobal); } int status = 0; // Processingif((status = linear.Run( )) < 0) {     linear.Print(“Error %d @ line%d\n”, status, _LINE_);     return ADAPTER_FALSE; } // Output if(lob.isMaster( )) {     myOutput StatSUM;     linear.Get_Output(StatSUM);     int       gSize = gGlobal.get_gSize( );    double       SUM_CT = StatSUM.get_SUM_CT( ),       SUM_CT2 =StatSUM.get_SUM_CT2( );     Double       Mean = SUM_CT / gSize,      StdDev sqrt((SUM_CT2 − SUM_CT * Mean)/(gSize − 1)),       StdErr =StdDev / sqrt(gSize);     cout.precision(12);     cout < < “Mean : ” < <Mean < < endl;     cout < < “Std Dev: ” < < StdDev < < endl;     cout << “Std Err: ” < < StdErr < < endl;   }   return ADAPTER_TRUE; }

The FirstProcess member function is the first function to be called whenthe code segment 80 is operating in a slave mode. The Global class ispassed to instantiate all global variables—the Global class is passed infrom the AddInput member function in the main part of the program.

5. The next member function, ProcesInputArray, generates random numbersso they are in the same alignment as would be provided in the sequentialportion 60 a of the application 60. double Random(void) {   return(double) rand( ) / (double) RAND MAX; } intLinear::ProcessInputArray(tRArray <myInput> &randNum,         const intfirst, const int last) {   for(int i = first; i < = last; i+ +) {  randNum[i] = Random( ); } return ADAPTER_TRUE; }

This member function is called before the main processing memberfunction to input data during runtime. This member function always runson a master machine—which guarantees the random numbers will match thesequential generation. The member function processes ranges, from firstto last, and will till the Input Array. The foregoing data is inputdynamically but in a different implementation could be coded so as topopulate the input array using a static input range.

6. The next member function, ProcessInputRanges, processes the range ofthe “for-loop.” The input to the function is the InputArray, and theoutput is the aggregation class on the one hand and the output processedrandom number on the other: int Linear::ProccesInputRanges(tRArray<myInput> &randNumArray,          myOutput &Range_StatSUM,      tRArray<myInput> &randArray,         const int first, const int last) { int  range_i; double     gMult = gGlobal.get_gMult( );   Range_StatSUM =0.;   for (range_i = first; range_i < = last; range_i+ +)   {     doublerandNum = randNumArray[range_i]. get_Num( );     double CT = randNum *gMult;     randArray [range_i] = CT;     Range_StatSUM + = CT;     //report progress     if (!Progress(range_i, last))     {     return −1;    }   }   return ADAPTER_TRUE; }

The above code in the “for-loop” matches the sequential code withrespect to processing the random number, storing it in the array, andaggregating the resulting numbers for the statistical calculation in theoutput. This membership function is run on the slave.

Further, there is a load balancing call, Progress, that informs thelobster engine 22 of the state of the processing loop. This informationis used to dynamically load balance the algorithm being executed by codesegment 80. This function can be user-defined to help the Lobster engine22 dynamically load balance the algorithm.

7. The next member function, ProcessOutputRanges, is the mainaggregation function which has, as inputs, the main aggregation class,the range aggregation and the OutputArray range received from theProcessInputRanges function. The ProcessOutputRanges function runs onmaster machine. int Linear::ProccesOutputRanges(myOutput &StatSUM,        myOutput &Range_StatSUM,         tRArray <myInput> &randArray,        const int first, const int last) {   StatSUM + = Range_StatSUM;  return ADAPTER_TRUE; }

To make the adapter 10 calculate the statistics required by code segment80, all that is required is a call to the member function,linear.Get_Output, which gets the main aggregation class (which wasaggregated in the ProccesOutputRanges function). Below is the outputsegment of the call segment 80. if (lob. isMaster( )) {     myOutputStatSUM,     linear.Get_(—) Output(StatSUM);     int       gSize =gGlobal.get_gSize( );     double       SUM_CT = StatSUM.get_SUM_CT( ),      SUM_CT2 = StatSUM.get_SUM_CT2( );   double     Mean = SUM_CT /gSize,     StdDev = sqrt((SUM_CT2 − SUM_CT * Mean)/(gSize − 1)),    StdErr = StdDev / sqrt(gSize); cout. precision(12); cout < < “Mean :” < < Mean < < endl; cout < < “Std Dev: ” < < StdDev < < endl; cout < <“Std Err: ” < < StdErr < < endl; }

The user selects adapters for each algorithm in the application 60 thatthey wish to parallelize. The choice of adapters includes simpleparametric systems (in which the problem is composed of a series oftasks which can be processed independently, much like SETI@home-typecalculations), and complex tree-structured recursive systems in whichall of the computations are interdependent and intertwined (typical offinancial models, pharmaceutical modeling, weather modeling, and otherreal-world problems). Should the user be unable to use one of theadapters in set 10 to achieve algorithm parallelization, an adapter SDK(System Developer's Kit) 12 is provided to permit the user to formulatean appropriate adapter.

The developer does not try to design or implement a parallel algorithm.Rather he uses the adapter API to hook in the logic of his existingalgorithm in such as way that Lobster has the ability to execute thecomponent parts of the algorithm. Adapter API's are designed to allowthese algorithm components to be expressed to Lobster in the most directand simplest fashion.

The key components of the program 20 are the adapters 10 and the Lobsterengine 22.

Adapters are the software architecture that manage the specificrequirements of parallel computing for different types of algorithms.The invention provides customizable object or class libraries fordifferent types of algorithm structures. The adapters preferably areembodied as customizable-object client/server libraries 62 or lasslibraries of algorithms and quantitative methods that form a basis for aparallel application. Each Adapter defines a template for a specifictype of algorithm and provides developers with a framework for adaptingtheir applications to run in parallel by hooking (i.e., including) thelogic of the algorithm to be parallelized into the template. The adapterframework is preferably based upon a set of object-oriented,general-purpose algorithmically parallelized base class adapters. Toenhance or extend the adapter features one can just inherit the Adapterbase class.

The adapter software forms the high level control structure of thealgorithm, with the constituent elements being encapsulated in functionsand data passed through function parameters such that these elements canbe executed on remote computers.

Lobster (Load Balancing Sub-Task ExecuteR)

The program 10 uses an underlying distributed framework called Lobster(Load Balancing Sub-Task ExecuteR). Lobster is a workload manager, andmanages all the generic management issues in an application. It takesresponsibility for a piece of work and ensures that it gets completedusing available resources with full fault tolerance and efficient loadbalancing, leading to a very efficient speedup in processing theapplication 60′.

Lobster is an integrated mechanism to distribute portions 60 a, 60 b,etc., that is, slices of a computation, across a network ofcomputational resources (such as a collection of Linux boxes, Suns,mainframes, whatever) to ensure that each portion of a program iscompleted using available resources and to ensure that fail-over,recovery, and other critical services are managed on behalf of theapplication. Lobster treats each part of the algorithm as a portion thatcan be transferred to another machine in case of failure or in case moreresources become available.

Lobster controls the amount of parallel computation dynamically inresponse to the direct computational complexity of the application. Forexample, the Linear Adapter 10C can be used to interpret the internalstructure of an application for traditional or hybrid approaches toparametric computing. Lobster then controls the amount of parallelcomputation dynamically in response to the computational depth of theapplication as determined by the linear adapter's having parsed throughthe algorithms within the developer's application and separated theminto multiple portions each having an associated time-step forexecution. Control is manifested by Lobster allocating these portionsdirectly in view of the time-step of each portion and indirectly in viewof and/or in response to resource utilization (e.g., how slowly is theportion running on the allocated machine).

Lobster provides the functionality to easily convert existingalgorithm-based applications into parallelizable applications byhandling the mapping, load balancing, fault tolerance and scalability.Specifically, converting algorithms into parallel algorithms involves:dynamic parsing of algorithms (in contrast to applications) intomultiple pieces; mapping and distributing the algorithm pieces todifferent network machines; balancing the allocation of the distributedalgorithm pieces; creating fault tolerance for the distributed algorithmpieces; and managing system errors. Lobster holds problem data in a“pool”; requests parsing of problems by sub-task size selected for loadbalancing; maps sub-tasks to machines; handles fault tolerance; andprovides task termination (e.g. upon lack of progress). In this way,Lobster exploits the appropriate level of parallelism for a givensituation by intelligently distributing the workloads to the mostefficient processors.

Lobster takes full advantage of existing middleware such as MPI, as canbe appreciated from the following example.

FIG. 3 is a graphical representation of the core architecture of theprogram 20 embodying the present invention. A lobster engine 22 handlesall generic parallel computing issues. Pieces of work are inserted intothe system, allocated to remote computers 1, 2, 3, etc. for processing,and the results are returned to the master for presentation to the nextlayer of software. All work comprises anonymous, unstructured blocks ofmemory. The lobster engine 22 can not manipulate the work in any wayitself, except for sending it over the network 4 to remote computers.The core parallel-computing requirements that apply to all types ofproblems, such as splitting of work, allocating work to remotecomputers, load balancing and fault tolerance are all handled by theengine 22 and are therefore available for all problem/algorithm types.

The work required by each code segment 80 must be manipulated throughexternally ‘plugged in’ routines which are designed to handle specificproblem structure, e.g., linear or tree structured problems. Wheneverthe lobster engine 22 needs work to be split into small sections, forresults of tasks to be aggregated or otherwise handled, or for a pieceof work to be processed to produce a result, these routines are calledto do the work. These data handling routines are in the adapter. Thelinear adapter acts as an agent to the lobster engine 22 formanipulating linear type problems on request. Likewise the tree adapteracts as an agent for manipulating tree structured problems on request.

Any concept specific to an adapter, such as the linear adapter aggregatemechanism are present only in the adapter code. Issues relating to workallocation, load balancing etc, are present only in the lobster code.The joining of these two layers creates a powerfully efficient andextendable framework for developing parallel applications.

The adapters manipulate a number of specific data types. The corelobster engine also manipulates a number of specific data types, thoughnot the same ones as the adapter. A fundamental aspect of the thearchitecture of program 20 is that the lobster engine 22 does not needto know the adapters' data. Rather it treats the information that itworks with as anonymous chunks of data, always using the adapter'sfunctions to manipulate the data, as required. For convenience, the sameterms are used in describing the adapter and the core lobster engine.

We now describe the operation of the lobster engine 22 when used with alinear adapter 10 c and a fix tree adapter 10 a. To facilitate thefollowing discussion, the following data types are employed:

No_of_tasks—the number of pieces of discrete work which compose theproblem

Root-scalar: a constant specified at initialization, made available toall slaves and fed into all functions for reference. It carries globalproblem information

Input_array-array: optional array specifying one input data element foreach task. These are specified by the user and form the input data tothe algorithm

Results_array-array: array of results, one data element for each task.These are the output from the algorithm.

First & Last-coordinates describe a range of tasks.0>=first>=last>=No_of_tasks-1

Aggregate-scalar: memory containing an aggregation of an array ofresults

Aggregate_array-array: this is an array of aggregates. Individualaggregates are returned (optionally) by slaves and are an aggregation ofthe results of the tasks processed by that slave task list. (Each slaveprocesses many separate lists of tasks in its lifetime). The aggregatearray is the total list of aggregate, is of arbitary length, and ispresented to the user's master process through Linear_GetResults, readyto be aggregated into a single aggregate.

The lobster engine 22 itself has data types, including a Task which iscomposed of a Task_list (i.e., a list of tasks to be processed) and aResult_list (i.e., a list of results of processed tasks), and a Globaldata which is given to each slave. The Global data maps to the linearadapter's root data.

We use “&” to signify an output parameter in function calls.

The short code example illustrates the parallelization of a simplemultiplication program that the adapter 10 operates upon. It multipliesevery element of any array by 7. Function: User_application( ) {   setupinput array   For (I=0; I<20; I++){     Result[I] = Input[I] * 7;    Aggregate + = Results[I]   }   Output result array }

The “for” loop processes every element of the array independently, witha simple mapping from inputs to outputs, and totals the resultantvalues. The lines of code in the “for” loop are moved into a separatefunction which is hooked into the linear adapter 10 c. This allows thelobster engine 22 to call this function on any slave computer on theremote network 4. The application 60 sets up the adapter at the mainentry points, telling it how many tasks our algorithm includes (namely,20 in this example), how many passes there are in the input array, andthen tells the lobster engine to run the code segment 80.

Thus, when rewritten to utilize the linear adapter, the function“UserApplication( )” now reads as follows: Function: User application( ){   ....   id = getID( )   if (id = = master)   {     Initialize rootnode and input data array[20]     call Linear_setup(tasks = 20,root_node, input_array)   }   call Linear_run( )   if (id = = master)  {     call Linear_GetResults(&results_array, &aggregate_array)    print results   } } // The following user routine will be called byslave processes. It generates // corresponding results in theresults_array for each element of the input_array Function:process(root, input_array, &results_array, &aggregate, first, last)   {  zero aggregate   loop from first to last   {     results_array[loop] =input_array * 7     total results_Array[loop] into aggegate     // Tellslave lobster library how much work we have done.     // This is part ofthe extrapolation load balancing mechanism     call PROGRESS(loop)   } ]

So far, we have adapted a simple multiplication program to utilize theadapters of the present invention. When executed, the function“UserApplication( )” calls another adapter function, namely “Linear_Run()” or “FixTree_Run”, for example. Regardless of which adapter functionis called, these latter functions invoke one of two lobster functionsthrough a callback (or membership function), depending on whether theinvoking code segment is a master or a slave. Exemplary calls are shownbelow.   // Solve problem   Function: Linear_run( )   {     if (I am themaster)     {       call master_run( )     else     }       callslave_run( )     }   } // Solve problem Function: FixTree_run( )   {  if (1 am the master)   {     call master_run( )   }   else   }    call slave_run( )   } }

Turning next to the lobster engine 22, that engine operates throughcallback functions installed by each caller (i.e., each adapter 10) toimplement a parallelized process.

The lobster engine 22 is based on conventional process-farm techniques.Work is held in a pool on a master process. Slave processes areallocated more work on a first come—first served basis as they becomelow on work. Slaves request more work from the master once they havecompleted processing of, say, 75% of the current work load. Byrequesting more work before the current work load process as completed,a new block of work will be received before the current one has finishedprocessing. Thus communications and processes are overlapped and theslaves do not lose time waiting for messages from the master process.

The work pool contains a list of chunks of work, each with a clearlydefined size. Where possible, existing chunks of work are allocatedintact from the pool to slave processes. Where this is not possible, apiece of work is split down to the required size, using the adapters'split function, i.e., a function that responds to a reference thatoriginates with the lobster engine 22, say, to provide the lobster withwork. More particularly, the lobster engine 22, through its dynamicparsing and mapping functionality 24, can issue a generic split requestwhich causes different ones of the adapters (e.g., adapters 10 a or 10c) to respond with their associated, respective split function (i.e.,process, process array or process subtree). Unlike the conventionalprocess-farm approach, lobster does not request that work be split untilthere is a run-time need for a small piece of work to be broken off.This means that work is split with knowledge of the specific volume ofwork that has to be split. This allows for an infinite granularity ofwork splitting and, thus, of load balancing.

Any splitting is coupled with an accurate load balancing mathematicswhich, provided with information about the speed and current amount ofwork on each of the slave processes, can split work in such a way thatall slave processors will finish processing the problem at exactly thesame time, providing an ideal optimum load balanced performance.

The load-balanced algorithm is kept informed of the speed and progressof each slave with a regular periodic message that is sent from eachslave to the master. If appropriate, the adapter will provide the userapplication with API mechanisms that allow the user to keep the adapterinformed about the volume of work that has been processed. The adaptercan then provide this information to the slave Lobster component, whichin turn can send that information to the master.

In order to take advantage of dynamic environments, Lobster allowsmachines to be added or removed seamlessly. New machines can be added tothe application while it is running, and failed tasks can be replaced.Work is simply moved in and out of a ‘work to do’ queue on the masterprocess. Lobster ensures that all necessary problem data is available toa new computer that joins the cluster part way through execution.Lobster operates in heterogeneous computing environments, and handlesconversion of data between different computer architectures.

Lobster sends ‘global’ problem data to each of the slave processes. Thisis constant data common to the algorithm that all slaves may need accessto. The adapter also uses this core lobster feature to send master-sideadapter information to the slave-side adapter library 62.

To provide load balancing, a conventional process farm is used with verylarge work sections, reducing network traffic. The final allocation ofwork to each process is performed by carefully sizing each task so thatall processes complete work at precisely the same time. This is achievedthrough extrapolation based on machine performance and monitoring of theamount of work still unprocessed on each machine. Work is recalleddynamically from slave processes to correct imbalances in the load, asLobster continually reassesses the environment using algorithms tooptimize performance at any given point in time.

Lobster also provides fault tolerance and manages fault tolerance usinga process that cooperates with a fault tolerant database 14 of the tasksthat it monitors. When a slave task dies, that piece of the applicationis automatically rerouted to one of the remaining processors so that itswork goes back into the pool. When the master dies, the slaves closedown. If a slave stalls, the master detects this using progress counter,with the application periodically indicating its progress. If the masterdoes not receive the slaves progress update message within a pre-setperiod of time, the slave is assumed to have stalled and it is removedfrom the system. If a slave dies or is removed, its work is retuned tothe work pool to be allocated to other slave(s). If the master stalls, athread detects the lack of progress and kills it. For example, slaveprocesses detect this using a timeout mechanism based on a keep alivemessage that is periodically sent to the slaves from the master.Partially processed results are delivered to the master task forprocessing. I.e., unit of results delivery is independent of the unit ofwork allocation/load balancing. Dead tasks on machines are repaired in aPVM type environment. Error logs and overall status information arecreated by the software. A configuration file is used to allow the userto control various aspects of software execution.

Scalability is provided through an automatically applied construction ofa hierarchy of sub-master processes, each supervising a group of slavetasks.

Problems are submitted to the system and held in a queue. They areallocated to groups of machines in a cluster, whether on dedicated ornon-dedicated networks, as machines become available. The size ofclusters can vary dynamically and Lobster will add or remove thesemachines from its cluster. Scheduling can occur over a singlecommunications cluster, or LSF style by providing a different clusterinstance for each application.

The parallel environment can be monitored, configured and controlledcentrally. Software is automatically uploaded and the environment (filesand environmental variables) automatically configured as needed.Applications are cached on machines commonly used for cluster computing.Overhead left behind by a terminated application is tidied by thesystem. All results, error reports and performance information areavailable in the system. Errors and performance statistics are gatheredand can be routed to appropriate people, through email or internalmechanics, e.g., users, administrators, and ourselves.

Below, we provide pseudocode for a lobster engine 22.   Master // Set-upproblem - master side // The initial input_list is a description of theentire problem that must be solved. // It has an associated size. For alinear adapter, this will be the number of tasks //in the problem. Fortrees, it is an arbitrarily high value representing the relative // sizeof the whole tree. The next operation(s) to be carried out of this inputnode // will be to apply the adapter's split function to break it downinto sections. Function: Master_setup(global, initial input_list) {  store global data for later distribution to slaves   Set in-put_listinto work pool } // Solve problem - master side. Once run by theadapter's run function, this will // solve the problem, by iterativelybreaking sections of work and sending them // to slaves, and receivingresults from the slaves. The problem can not be // manipulated in anyway except through the adapter's split (on master) and // process (onslave) functions. The master works with task_lists and results_list //which are linked lists of anonomous blocks of memory, supplied by,distributed for, // manipulated by, arid ultimately returned to, theadapter. Function: Master run( ) {   Initialize   Send global to allslaves   Call Calculate_load_balanced_work_allocations( )   Loop throughslaves,   {     Call dispatch_work_to_slave( ) to send first block ofwork to each slave   }   Loop until (all work is complete)   {    Receive message from slave     Act on message:     If message is‘slave is low on work’       Call dispatch_work_to_slave( ) to sendfirst block of work to each         slave     If message is ‘resultsreceived from slave’       Unpack results_list from message       Calladapter_receive_results(results_list) and pass results to adapter forstorage, processing or passing to user     If message is ‘slave progressupdate’       Keep record of slave progress for use in load balancecalculations     If message is ‘machine lost’       Push data from thatmachine back into work pool   } } // Calculate ideal volume of work togive to slaves in future work allocations Function: load balanced workallocations( ) {   Extrapolate each slaves progress based on lastreported progress and speed   Calculate amount of work to give to eachslave so they will finish at the same time } // Build task_list and sendto slave. The load balancing logic has determined how // much workshould be given to each slave. This is a purely numeric process. // i.e,x% of the work pool should be allocated to each slave. This functionmust // run through the list of available blocks of work, each of whichhas associated with // it a volume, and decide which blocks to send tothe slave. If the required volume // can not be met through theconsecutive sequence of nodes, then the node is // split into the parts,the first part being the amount needed to complete the volume // aboutto be dispatched to the slave and the other half is the remainderFunction: Dispatch_work_to_slave( ) {   Lookup what quantity of workfrom the pool must be passed to the slave   New slave task_list   Loopthrough pool until we have enough work for the slave   {     If piece ofwork is smaller than required amount     {       Remove task from pool      Add task to slave task_list       CallAdapter_get_input_array(&input_array) and add to task_list     }    else     {       // Split chunk of work up according to requiredamount       Remove task from pool       Call adapter splitfunction(task, new_task_list, remaining_task_list)       Addnew_task_list (the broken off section of work) to slaves          task_list       Add remainig_task_list back into work pool      call Adapter_get_input_array(&input_array) and add to slavestask_list     }   }   Send the task_list to slave } Slave // Runproblem - slave side Function: Slave_run( ) {   Initialise   Receive andstore global data from master   Give global to adapter   Loop untilmaster tells us to finish   {   Get message   Act on message   Ifmessage is ‘master has finished’     Return from slave_run   If messageis ‘new work has arrive’     Unpack task to first, last, input_array    Loop through tasks     {       Call adapter_process(task_list,results_list) callback to process work     ]     Send results_list tomaster   } // Called by user to indicate progress made with thetask_list being worked on Function: PROGRESS(progress) {   Send messageto master to indicate the slave progress to the lobster engine 22. }

Finally, a brief discussion of how the adapters 10 interface with thelobster API is provided.

Each of the adapters 10 must present an interface to the lobster engine22. This includes inserting an initial block of work into the system,providing a split function to breakup work into sections and areceive_results function to accept results that are returned by themaster lobster library. The split function for linear problem is atrivial co-ordinate and memory manipulation routine. The receive_resultsfunctions must store received results and aggregate them in an arrayready for later retrieval by the user. Additional optional userapplication callbacks may be installed to provide input_array data andreceive_results on demand as the lobster executes the problem. These canlead to improvements in performance and memory requirements.

In the following pseudocode, various calls by the user application 60′invoke processes within the adapters 10 that, in turn, cause the lobsterengine 22 to initiate and manipulate the code segment 80. Likewise, somecalls can be from the lobster itself to an adapter 10 which, in turn,cause the lobster engine 22 to initiate and manipulate the code segment80. Master Run-Time Mode // Called by user to set-up problem Function:Linear_setup(no_of_tasks, root, input_array) {   Store setup parametersfor use in the adapter   Set input_array and first,last coordinates intoinitialize signel node task_list   // root becomes the master's globaldata   Call Master_setup(root, task_list) } // Called by master lobsterto request breakdown of a piece of work Function:Adapter_split_function(task, % to split, output_task_list,remaining_task_list) {   split requested volume from task   split intotwo parts, the output_task_list being of volume X and theremaining_task_List holding the rest } // Called by master lobster topresent results back to adapter Function:Adapter_receive_results_function(task_list, results_list) {   Decodetask description (first and last coordinates) from task_list   Decodecorresponding results from results_list - separating aggregate andresults_array   Store results_array at correct location in adapter'soverall array   Store aggregate in adapter's overall aggregate array }// Called by user to retrieve results after processing has finishedFunction: Linear_GetReults(&results_array, &aggregate) {   Returnresults array and aggregates_array to user } // Called by master lobsterto retrieve input array data prior to dispatch task_list to slaveFunction: Adapter_get_input_array(&input_array) {   Copy user specifiedinput_array into parameter } Slave Run-Time Mode // Process task list onthe slave using the users process function Function: Adapter_processfunction(task list, &results list) {   Extract coordinates (first, last)from task_list   Extract input_array from task_list   Allocateresults_array   Call user_process_function(root, input_array,&results_array, &aggregate, first, last)   Set results_array intoresults_list   Set aggregate into results_list }

The foregoing discussion largely concerned the linear adapter. Asanother example, a tree adapter can be used to allow tree-structuredproblems to be solved. Tree problems are defined by a single intitlalroot node, which can then be broken down into a finite number ofchildren, each of which is itself a tree. Parsing the tree datastructure is performed through application of a user supplied splitfunction which can split a node into its consituant children nodes. Thetree adapter callback functions are used to split and merge sub-treesand process leaf nodes, or whole sub-trees. The tree adapter handles alladministration needed to track dept between sub-trees. The tree is splitinto variable sized sub-trees rather than split completely to a fixeddepth. This reduces the number of split operations that are required andmaximizes performance. An optional user routine is allowed forprocessing bottom row sub-trees of depth 2.

The whole algorithm can be mapped to a single data structure or splitinto input, output and ‘merge’ data. Merge data is generated in a nodesplit and fed through to a node merge, without passing though theprocess function. Trees are processed either by the client applicationor by an interactive stack-array based algorithm, which traverses thetree, solving through the client's leaf processing function.

The following pseudocode is specific to the use of tree adapters andinvokes the lobster engine, either when the adapter is in a master orslave run-time mode. Master Run-Time Mode // Called by user - setupfixed tree problem Function: FixTree_setup( ) {  Store setup parameters} // Called by master lobster to breakdown a problem Function:Adapter_split_function(task_list, &new_task_list, &remaining_task_list){  Traverse tree using user split callback to split nodes  Returnsub-lists in two lists, the broken off section and the remainder } //Called by master lobster to receive results that come back from slavesFunction: Adapter_receive_results(results_list) {  Slot results intolist  When all siblings are present   Call user merge function toproduce a results from the child results  When root results is produced,store it } // Called by user to retrieve results after problem is solvedFunction: FixTree_GetResult(&root)  Return root result } Slave Run-TimeMode Function: Adapter_process_function(input_array, &results_array) { Traverse tree, processing to completion, calling user split, merge andprocess callbacks }

The fixed tree adapter 10A presents an API ideal for handling treestructured (e.g., recursive math) problems. In selecting an appropriateadapter 10 for a given algorithm to he parallelized, the benefits andtradeoffs of a given adapter are considered as they apply to a givenalgorithm type.

The user problem is handled indirectly through callback functions tosplit and merge sub-trees and process leaf nodes, or whole sub-trees.The problem structure (tree node) is implemented in the clientapplication giving Lobster complete freedom from application specifics.In the tree specific split, process and merge functionality are providedas services to the lower level generic core-lobster system, which inturn drives the problem solving process using these routines. The treeadapter handles all administration needed to track dependencies betweensub-trees. The tree is split into variable sized sub-trees rather thansplit completely to a fixed level allowing for very efficient splitting.The adapter handles memory allocation of nodes for splitting. Trees maybe pruned midway through processing. An optional user routine is allowedfor processing bottom row sub-trees of depth 2. The whole problem can bemapped to a single data structure or split into input, output and‘merge’ data. Merge data is generated in a node split and fed through toa node merge, without passing though the process function. Trees areprocessed either by the client application or by an interactivestack-array based algorithm, which traverses the tree, solving throughthe client's leaf processing function. Static global problem data isaccepted from the master task and distributed to each slave as it startsup.

Referring now to FIG. 7, the general scheme utilized in launching aparallelized application is illustrated in connection with anapplication 60 that utilizes a linear adapter in order to perform a wordcount of text in a data file, via a portion 60 a of the application. Theapplication 60 has a program flow as indicated by the arrow A. Duringthe course of the execution of the application, the crosscaller (client)interface is instantiated with the name of the adapter used to implementportion 60 a (which, in this case, is a linear adapter). Also, inputdata objects including, for example, a Global object and an array, aresent through the xcaller (which in this example include the number ofparagraphs; input array of paragraphs; etc.). The xcaller uses theadapter name to launch the adapted (that is, parallelized version ofthe) code segment 80 a. These steps are indicated by arrow 710.

The Adapted code segment 80 a is launched on a first resource availableto the application 60. That resource can be the same or anotherprocessor resident on the machine that is executing application 60, orcan be another machine connected via a network 4. The lobster object isinstantiated in the code segment 80 a, as indicated by arrow 720. Inpart, this includes determining if the lobster object is operating on aserver in a master mode or a slave mode. Since this instance is thefirst lobster instance, the lobster resident in the code segment 80 a isa server operating in a master mode (“master server”). The adapterobject of code segment 80 a instantiates the xcaller and then receivesthe input data. Then a linear adapter 10 c is instantiated (in thisexample) with the operating parameter being the size of the array toprocess, i.e., the number of paragraphs to analyze, the text of theparagraphs, etc.). This global input data is added so that it can bemade available to any processes that are to handle the portion 60 a,namely, each code segment 80 a, whether it be a master or a slave.

With the set-up of the master code segment 80 a complete, the lobstercan execute the processes necessary to implement the algorithm at hand,here, the word count routine. To do this, the lobster launches at leastone copy of the adapted code on a different resource, for example, adifferent processor or a different machine on the network 4. This isindicated by arrow 730, which causes another instance of the codesegment 80 a to be instantiated as code segment 80 a′.

As shown by arrow 740, the new instance code segment 80 a′ instantiatesitself with the lobster and adapter objects. Before the lobster isinstantiated, the code segment 80 a′ comprises a stateless sever readyto assume either a master mode of operation or a slave mode ofoperation. The code segment 80 a′, and more generally, the replicatedcode segments that are used in this invention are intellegent workersinsofar as they have their own capacity to determine, in response toparameters passed to them and operating conditions in the network inwhich they reside, the optimum mode for their respective operation. Inpart, this enables load balancing and fault tolerance among the activesegment in real-time.

Once the lobster and adapter objects are instantiated, the code segment80 a′ operates either (1) in a single mode in which it serves as a slaveto the code segment 80 a master, or (2) in a dual mode in which itservers both as a slave to the code segment 80 a master and also as amaster to further code segments 80 a′″ that are later instantiated bythe code segment 80 a′ in order to assist 80 a′ in processing a portionof work. The dual mode of operation generally has applicability wheneverthe adapter object is not a linear algorithm. The code segment 80 a′then runs, ready to process a portion of work that is to be provided toit.

Arrow 750 illustrates a first callback by which the master code segment80 a can send any global input data to each of the instantiated slaveservers 80 a′ (only one shown in FIG. 7), if such data exists. This datais sent to all slaves because each slave needs that information operateon the algorithm.

Arrow 760 illustrates a second callback by the code segment 80 a′ towhich the master code segment 80 a responds with data to be processed,if it exists. The data could be an input array on the other hand, or canbe streamed (e.g., on-the-fly) data from a conventional data feed (e.g.,real-time stock price data, weather, etc.).

Arrow 770 illustrates the callback to initiate the processing andaggregation of data concerning the problem at hand (e.g., the countingand totaling of words in the file). In part, this includes Progressreports made by the adapter object in the code segment 80 a′. In themeantime, the code segment 80 a is monitoring the progress report anddistributes additional portions of the work in the pool to the codesegement(s) 80 a′. Work is maintained at within the hierarchy ofsegments 80, 80′, 80″, etc. in respective pools.

Arrow 780 represents the results of the processing and any aggregationat the code segment 80 a′ to the code segment 80 a. Also, the codesegment 80 a aggregates results received from each of the code segments80 a′. After the results are transferred, the code segment 80 a′ processcan be terminated, as represented by arrow 790.

With further reference to FIG. 7, additional code segments 80 a″ areillustrated which may be useful in some embodiments of the presentinvention. Specifically, there are a number of adapter objects such asthe the fixed tree adapter object and the lattice adapter object whichsupport a dual-mode role for a code segment 80 a′, as noted above. In adual-mode embodiment, the code segment 80 a′ operates as an activeserver. On the one hand, it is a slave to the code segment 80 a, and onthe other hand as a master to hierarchically subservient code segments80 a″ (and possibly 80 a″, etc.). In FIG. 7, the arrows 730-790 areillustrated as a single arrow merely for ease of illustration, butcommunication is the same as previously described.

DNET (Distributed NETwork

Also present in each program is virtual middleware. In the presentexample, this has enabled peer-to-peer communication among the computers1-3. In the preferred embodiment, the virtual middleware is called DNET(Distributed NETwork). DNET is used to send and receive messages, packand unpack the data into them, and is also used to monitor the health ofremote processes. Its messaging interface is based on the PVM standard.Its implementation maps the DNET API onto (parallel virtual machine) PVMor MPI. PVM and MPI allow adapters to be constructed that makeinter-slave communications available to their applications. For the MPImapping, all packing and unpack is implemented inside DNET with the MPIbeing used to send character buffers. Threads are used to provide faulttolerant timeout safe guards on top of the MPI send and receivecommands.

DNET virtual middleware provides a virtual image encapsulating manydifferent computing cluster middlewares, which may be located indifferent places. DNET offers a unique technology solution making iteasy for a parallel application to work with any type of cluster. DNETprovides for flexible deployment on different cluster communicationplatforms, and therefore highly deployable on outsource computing. DNETprovides flexible multiple interfaces to applications and the Lobsterplatform. DNET provides scheduling and queuing on non-dedicatedcomputing environments.

Parsing a problem into sub-tasks is handled by size rather than inrelation to an adapter's view of the data structures involved. Lobsteruses a master task to control the system, allowing application controland observation of the executing applications. This means the softwareis fully embeddable into an application. The problem is split throughiterative application of the split function into a collection ofsub-trees according to the size required.

DNET includes various auxiliary technologies, which extend options fordeployment, especially for outsourcing work, and creates a more flexibleoperational environment. Auxiliary technology includes scheduling andqueuing, central control encapsulated environment, communicationssystems mapping, and separable multiple interfaces.

Applications have inter-process communication based external interfacesseparate from their applications. DNET maintains a database of executingapplications. Users can connect into existing applications or start newones. The GUI logic is uploaded automatically if not already present.The GUI can connect and disconnect at will from any computer, anywhere.The distinctions between batch and interactive applications aregeneralized. The running application will block if it requires userinput, until the user reconnects. The same application can be used bydifferent types of GUI, even during the lifetime of a single instance ofthe application. Interfaces include HTML, CGI, Java, C/C++, DLL's,propriety socket based interfaces, Telnet.

At the DNET middleware level, the Scheduler submits problems to thesystem and holds them in a queue. They are allocated to groups ofmachines as machines become available. Software can map at run time on aPVM or HP-PVM type cluster communications environment. All results,error reports and performance information are available in the system.

xCaller (Cross Caller

The xCaller (cross caller) is a client/server type mechanism that allowsan interface program to spawn-off and communicate with an application.The program may be spawn-off on the local machine or submitted into abatch queuing system. The xCaller handles hetergenious data conversionwhen the application is spawned-on a different architecture to theinterface. Specifically, the cross caller provides an interface betweenthe parallelized application 60′ and the code segments 80, 80′,permitting call backs therebetween.

xCaller maintains a database of executing applications. Users canconnect into existing applications or start new ones. The GUI logic isuploaded automatically if not already present. The GUI can connect anddisconnect at will from any computer, anywhere. The distinctions betweenbatch and interactive applications are generalized. The runningapplication will block if it requires user input, until the userreconnects. The same application can be used by different types of GUI,even during the lifetime of a single instance of the application.Interfaces include HTML, CGI, Java, C/C++, DLL's, propriety socket basedinterfaces, Telnet.

The approach of the preferred embodiment of the invention issignificantly different from existing parallel computing softwareapproaches which do not provide this type of flexibility and whichprimarily use a proprietary rather than a standards-based approach.Using the approach of the preferred embodiment avoids the need to investin expensive high-end computing hardware or development of newapplications designed for parallel computing in order to solve complexproblems. This system allows for easy integration with existingenterprise customer software. This facilitates a low cost of entry forenterprises by permitting customers to merely modify existing coderather than writing new software solutions. The present inventionbridges the gap between parallel application development and clustercomputing.

1. A computer program on a computer readable medium for parallelizing anapplication, the computer program comprising: a code segment forproviding an adapter with a plurality of processing functions; a codesegment for associating the adapter with a function within anapplication, wherein the association between the adapter and theassociated function is based on correlation between the associatedfunction and one of the plurality of processing functions; a codesegment for adapting the application to conform to a plurality oflogical components, at least one of the plurality of logical componentsbeing encapsulated by the adapter and at least one of the plurality oflogical components including non-parallelized or non-adapted code; acode segment for creating multiple instances of each of the plurality oflogical components; a code segment for distributing the multipleinstances of each of the plurality of logical components for parallelexecution across a plurality of discreet systems or a plurality ofprocessors in a single system; and, a code segment for monitoring andbalancing the parallel execution.
 2. The computer program of claim 1further comprising a code segment for identifying the function withinthe application to adapt such that the adapter will parallelize theexecution of such function.
 3. The computer program of claim 1 whereineach code segment is executed on at least one processor during run-time.4. The computer program of claim 1 further comprising: a code segmentfor using one of the multiple instances with respect to one of theplurality of logical components as a master and the remaining multipleinstances as slaves; a code segment using the master to communicate withthe slaves in order to retrieve execution information from the slaves,the execution information including information specific to applicationprogress; and, a code segment for using the master to provide adaptivecommands to the slaves based on the execution information in order tooptimize execution performance of the slaves.
 5. The computer program ofclaim 1 wherein a software engine is included in at least one of theplurality of logical components to support the adapter, wherein thesoftware engine is configured to cooperate with the associated adapterto control and supervise distributed processing functions and furtherwherein computational and execution environment information is includedin at least one of the plurality of logical components.
 6. The computerprogram of claim 5, wherein the distributed processing functions includeat least one of data mapping, serialization, data and rangedistribution, and stall and error detection and correction.
 7. Thecomputer program of claim 5, wherein the distributed processingfunctions coordinate results of the parallel execution with respect tothe distributed multiple instances corresponding to the plurality oflogical components in real-time and return said results.
 8. A computerprogram for running an application, the computer program comprising: acode segment for associating an adapter with a portion of an applicationwhich has been identified for parallelization, wherein the adapter isconfigured to provide a plurality of processing algorithm typefunctionalities; a code segment for creating a master including theadapter and remainder code portions of the application not identifiedfor parallelization; a code segment for using the master that operatesin a master mode to instantiate a plurality of stateless slaves forparallel execution, each stateless slave including a clone of themaster; and, a code segment for directing the master to distributeadaptive commands to the plurality of stateless slaves to adjust theparallel execution based on the progress of the parallel execution. 9.The computer program of claim 8 further comprising a code segment foridentifying a code portion of the application for parallelization. 10.The computer program of claim 8 further comprising a code segment forreporting the progress of the parallel execution with respect to theplurality of stateless slaves to the master, the progress includingprogress information with respect to the clones.
 11. The computerprogram of claim 8 wherein the adaptive commands include data and rangeinformation.
 12. The computer program of claim 11 further comprising: acode segment for monitoring the progress of the parallel execution withrespect to the plurality of stateless slaves after the adaptive commandshave been received by the plurality of stateless slaves; a code segmentfor adjusting and re-distributing the adaptive commands including thedata and range information to the plurality of stateless slaves based onthe monitored progress; and, a code segment for committing the adaptivecommands to an optimal level for the parallel execution with respect tothe plurality of stateless slaves once an optimal performance level hasbeen reached.
 13. The computer program of claim 8 wherein each statelessslave further includes a software engine configured to cooperate withthe clone of the adapter to control and supervise distributed processingfunctions; and wherein each stateless slave further includescomputational and execution environment information.
 14. The computerprogram of claim 8 further comprising: a code segment for distributingthe plurality of stateless slaves for parallel execution across aplurality of discreet systems or a plurality of processors in a singlesystem.
 15. The computer program of claim 8 wherein each code segment isexecuted on at least one processor during run-time.
 16. A computerprogram on a computer readable medium for parallelizing an application,the computer program comprising: a code segment for providing an adapterwith a plurality of processing algorithm type functionalities; a codesegment for identifying an algorithm within the application to adaptsuch that the adapter will parallelize the execution of such algorithm;a code segment for associating the adapter with the algorithm within theapplication, wherein the association between the adapter and thealgorithm is based on correlation between the algorithm and one of theplurality of processing algorithm type functionalities; a code segmentfor adapting the application to conform to a plurality of logicalcomponents, at least one of the plurality of logical components beingencapsulated by the adapter and at least one of the plurality of logicalcomponents including non-parallelized or non-adapted code; a codesegment for creating multiple instances of each of the plurality oflogical components; a code segment for distributing the multipleinstances of each of the plurality of logical components for parallelexecution across a plurality of discreet systems or a plurality ofprocessors in a single system; and, a code segment for monitoring andbalancing the parallel execution.
 17. The computer program of claim 16further comprising a code segment for identifying a function within theapplication to adapt such that the adapter will parallelize theexecution of such function.
 18. The computer program of claim 16 furthercomprising: a code segment for using one of the multiple instances withrespect to one of the plurality of logical components as a master andthe remaining multiple instances as slaves; a code segment using themaster to communicate with the slaves in order to retrieve executioninformation from the slaves, the execution information includinginformation specific to application progress; and, a code segment forusing the master to provide adaptive commands to the slaves based on theexecution information in order to optimize execution performance of theslaves.
 19. The computer program of claim 16 wherein a software engineis included in at least one of the plurality of logical components tosupport the adapter, wherein the software engine is configured tocooperate with the associated adapter to control and supervisedistributed processing functions and further wherein computational andexecution environment information is included in at least one of theplurality of logical components.
 20. The computer program of claim 19,wherein the distributed processing functions coordinate results of theparallel execution with respect to the distributed multiple instancescorresponding to the plurality of logical components in real-time andreturn said results.